feat: Add BDD (Behavior-Driven Development) semantic anchor#138
feat: Add BDD (Behavior-Driven Development) semantic anchor#138Nantero1 wants to merge 2 commits into
Conversation
Adds BDD as a standalone semantic anchor covering Dan North's collaborative specification practice. Distinct from TDD (developer solo practice) — BDD is team collaboration with Given-When-Then scenarios, three amigos, and living documentation.
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughDiese Pull Request fügt neue Dokumentation und Referenzmaterialien für Behavior-Driven Development (BDD) hinzu. Dabei werden drei Dateien geändert: eine neue BDD-Ankordokumentation, deren Include-Directive in der Übersichtsdatei sowie ein Katalogeintrag mit BDD-Referenzen. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/anchors/bdd-given-when-then.adoc`:
- Line 32: Die Aussage "Cucumber contributor" in der Zeile starting with "Key
Proponent:: Dan North (\"Introducing BDD\", 2006), creator of JBehave and
Cucumber contributor" ist ungenau; ändere den Text so, dass Dan North als
Urheber von BDD und Schöpfer von JBehave genannt wird und klar gestellt wird,
dass JBehave Cucumbers Design beeinflusste, während Cucumber selbst 2008 von
Aslak Hellesøy entwickelt wurde (z. B. ersetzen durch "creator of JBehave; his
work influenced Cucumber's design — Cucumber was created by Aslak Hellesøy in
2008").
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro
Run ID: c9cf5ee3-fb18-493e-8350-12d498c3d93e
📒 Files selected for processing (3)
docs/all-anchors.adocdocs/anchors/bdd-given-when-then.adocskill/semantic-anchor-translator/references/catalog.md
Dan North created JBehave which influenced Cucumber's design, but Cucumber itself was created by Aslak Hellesøy in 2008. Fixes CodeRabbit review comment.
|
Regarding the CodeRabbit finding on Cucumber attribution — valid, fixed in a9105ae. Dan North created BDD and JBehave, but Cucumber was created by Aslak Hellesøy in 2008. Updated the text to: "creator of JBehave which influenced Cucumber's design (Cucumber created by Aslak Hellesøy, 2008)". |
|
Review: ✅ Good anchor, merge-ready. BDD with the qualifier "Given-When-Then" makes this a precise, attributable anchor (Dan North, 2006). Good content, proper structure, nice distinction from TDD anchors. Post-merge TODO:
Merging recommended, translation will follow in batch (see #149). |
LLM-Coding#138, LLM-Coding#139) Content from @Nantero1's original PRs LLM-Coding#138 and LLM-Coding#139, rebased on current main after merging LLM-Coding#137, LLM-Coding#140, LLM-Coding#142, LLM-Coding#143. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Replaced by #152 (rebased on current main to resolve merge conflicts). Content is identical to your original PR. Thank you! |
3 participants
Summary
Why this anchor?
BDD activates: Dan North, specification by example, three amigos, Gherkin syntax, Cucumber/Behave, living documentation, collaboration between devs/QA/business.
Distinct from: Chicago School TDD (developer solo, state-based), London School TDD (developer solo, interaction-based). BDD = team collaboration + outside-in specification.
Files changed
docs/anchors/bdd-given-when-then.adoc— new anchor filedocs/all-anchors.adoc— added include in Testing & Quality sectionskill/semantic-anchor-translator/references/catalog.md— added catalog entrySummary by CodeRabbit
Dokumentation